Discover gists
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
- For speaking inquiries: arr@sugarpirate.com. I am interested in speaking about:
- TypeScript, JavaScript, React
- GraphQL
- Elixir/Phoenix, Microservices
- Engineering leadership/management
- Videos: http://bit.ly/talks-by-lauren-tan
- Slides: https://speakerdeck.com/poteto
| /** | |
| * Atomics & threads complement library | |
| * Matthew Reiner, 2026 | |
| * Available under the GPL 3.0 license | |
| * Targeting: Windows, Linux, FreeBSD, NetBSD, OpenBSD, MacOS | |
| * Implements the following: | |
| * - Wait/Notify functionality for simple types up to 64 bit | |
| * - Arbitrary condition wait | |
| * - Fine-grained memory ordering | |
| * - Thread management |
| BLACK => "\033[30m", | |
| RED => "\033[31m", | |
| GREEN => "\033[32m", | |
| YELLOW => "\033[33m", | |
| BLUE => "\033[34m", | |
| PURPLE => "\033[35m", | |
| CYAN => "\033[36m", | |
| WHITE => "\033[37m", | |
| # background color |
| "references": { | |
| "effect": { | |
| "repository": "Effect-TS/effect", | |
| "description": "Use for canonical Effect source, APIs, tests, and implementation patterns." | |
| }, | |
| "effect-monorepo": { | |
| "repository": "lucas-barake/effect-monorepo", | |
| "description": "Use for Lucas Barake's full-stack Effect monorepo patterns, composable policies, HttpApi contracts, Schema classes, and Layer composition." | |
| }, | |
| "accountability": { |
| Steps to Submit app to Google Play Store | |
| 1. Prepare your developer account. | |
| 1.1 Register for a Google Play Developer account using your Google Account (https://play.google.com/console/u/0/signup) | |
| 1.2 Once you have a Developer account, you can use the Play Console to publish and manage your apps | |
| 1.3 During the signup process, you'll need to review and accept the Google Play Developer Distribution Agreement | |
| 1.4 Pay registration fee. There is a $25 USD one-time registration fee that you can pay with credit or debit cards | |
| 1.5 Type your account details. Your "Developer name" is displayed to customers on Google Play. | |
| 1.6 You can add more account information after you've created your account. |
